-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
goocanvas: update to 3.0.0 #31159
goocanvas: update to 3.0.0 #31159
Conversation
I got this error:
Seems like gpredict would need a rebuild. Anybody know how to solve this? |
I didn’t update goocanvas to 3.0.0, because it breaks gpredict and perl-GooCanvas2 --> gscan2pdf. Building gpredict with goocanvas-3.0.0 errors out with: and perl-GooCanvas2 fails running tests with Haven’t looked into fixing those two packages, but without it goocanvas-3.0.0 cannot be merged. |
I see. I just tried on my machine for updating my package for akira. It worked so thought of committing the changes. Didn't know it has so many things attached to it. Arch Linux has recently moved to goocanvas 3. I think I got some hints. Arch's
To remedy this, something like this has to be added to template:
I haven't looked into |
If the above changes are ok, should this PR contain all the changes for updating to goocanvas 3? Or can the changes be in separate PRs for separate packages? In any case, let me know if I can help in anything. |
I think this PR should contain all the necessary changes, but in a separate commit per affected package. Just built |
|
As for Just tested it – this time really with goocanvas-3.0 ;) – and it works. However, a simple
|
Sorry again, got a little confused with old and modified packages on my system, but all sorted out now. ;) So, to summarize, with the two |
I think About that gpredict check error: the file it complains about, |
@newbluemoon
Seems to be related to translations. This didn't happen in my machine though. Any idea why this is happening? |
You probably didn’t use the |
Oh! I didn't see your comment. So I'm trying with something like this:
Also applying revision change... |
Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it. |
General
Have the results of the proposed changes been tested?